\documentclass[journal]{IEEEtran}
% *** GRAPHICS RELATED PACKAGES ***
%
\ifCLASSINFOpdf
   \usepackage[pdftex]{graphicx}
  % declare the path(s) where your graphic files are
   \graphicspath{{../img/}}
  % and their extensions so you won't have to specify these with
  % every instance of \includegraphics
   \DeclareGraphicsExtensions{.pdf,.jpeg,.png}
\else
\fi
\hyphenation{op-tical net-works semi-conduc-tor}
\renewcommand{\and}{\texttt{Android}}

\begin{document}
%
% paper title
% can use linebreaks \\ within to get better formatting as desired
\title{Wireless Network Project 2009-2010\\ Realization of a wi-fi take away application based on Android}

\author{By: Michele~Bortolato, Marco~Orlandin, Marco~Secchiero }

% The paper headers
\markboth{Wireless Network Project: Wi-Fi Take Away}%
{Shell \MakeLowercase{\textit{et al.}}: Bare Demo of IEEEtran.cls for Journals}
\maketitle


\begin{abstract}
This document shows the steps made during the implementation of a wireless network's project concerning the realization of a wi-fi application for managing orders from a take away. The application is developed for \texttt{Android} smartphone.
The report is structured as below:
\begin{itemize}
 \item The first part introduces the developed application, showing its utility and defining the problem, besides we list the development tool used;
 \item The second part regards the requirements analisys , it lists what the application do, separating requirements by category;
 \item The third part regards the project development, this section is divided in three parts, the first concerns the server, the second concerns the client's logic application and the last concerns the client's graphical layout. 
Each part lists the architectural specification including eventually sequence diagram to show communication between client and server;
 \item The fourth part regards the description of some issues met during the development;
 \item The fifth part shows some screenshot about a sample execution of the application;
 \item The last part concludes the document and tells some possible extension or improvement of the application, finally a brief remark about what each group component did and what activities he developed is given.
\end{itemize}

\end{abstract}
% IEEEtran.cls defaults to using nonbold math in the Abstract.
% This preserves the distinction between vectors and scalars. However,
% if the journal you are submitting to favors bold math in the abstract,
% then you can use LaTeX's standard command \boldmath at the very start
% of the abstract to achieve this. Many IEEE journals frown on math
% in the abstract anyway.

% Note that keywords are not normally used for peerreview papers.
\begin{IEEEkeywords}
Android, wi-fi, take away, Wireless Network
\end{IEEEkeywords}
% For peer review papers, you can put extra information on the cover
% page as needed:
% \ifCLASSOPTIONpeerreview
% \begin{center} \bfseries EDICS Category: 3-BBND \end{center}
% \fi
%
% For peerreview papers, this IEEEtran command inserts a page break and
% creates the second title. It will be ignored for other modes.
\IEEEpeerreviewmaketitle

\input{introduction}
\input{analisys}
\input{development}
\input{issues}
\input{execution}
\input{conclusion}
%texttt per classi e tutto

%Michele Bortolato
	%Abstract
	%Example of execution
	%Development.Server

%Marco Secchiero
	%-Introduzione
	%Development.Client.layout
	%Analisi requisiti

%Marco Orlandin
	%Development.Client.LogicalVew
	% Issues
	%Conclusioni


% Can use something like this to put references on a page
% by themselves when using endfloat and the captionsoff option.
% \ifCLASSOPTIONcaptionsoff
%   \newpage
% \fi

\end{document}


